feat(workflows): add helper and workflow to keep keystone and nautobot in sync #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm really not a fan of my approach with the tests. Maybe even the whole thing. Would be happy for some feedback on changes. @rackerlabs/understack-dev |
|
The requests-mock might not be catching all HTTP calls because it feels slow. |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
|
cardoe
force-pushed
the
keystone-event
branch
4 times, most recently
from
29045c2
to
ba2905e
Compare
|
So need some ideas on how to better check the workflow template against the schema. Otherwise I think this will work. |
cardoe
force-pushed
the
keystone-event
branch
2 times, most recently
from
1e888dd
to
54c91a4
Compare
cardoe
force-pushed
the
keystone-event
branch
14 times, most recently
from
0e9ba93
to
3772008
Compare
skrobul
reviewed
Sep 9, 2024
apps/understack-workflows/eventsource-openstack/sensor-keystone-event-project.yaml
Outdated
Show resolved
Hide resolved
python/understack-workflows/understack_workflows/main/sync_keystone.py
Outdated
Show resolved
Hide resolved
cardoe
force-pushed
the
keystone-event
branch
from
3772008
to
48c60cb
Compare
Be able to use this for testing.
Added a helper script to sync keystone domains to nautobot tenant groups and keystone projects to nautobot tenants.
This doesn't change any code or the actual service account that is being used but it defines it in a way that can be consumed by external secrets and sets the pathway for us to generate this in the future. We'd need either an operator to action on the service account secrets to keystone or some other way to keep them in sync.
Added an EventSource listener for keystone notifications. Added a Sensor to trigger a workflow to be run when projects are created, updated or deleted in keystone. Added a workflow to execute the keystone sync script on each of those triggers.
cardoe
force-pushed
the
keystone-event
branch
from
48c60cb
to
431e8b6
Compare
skrobul
approved these changes
Sep 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a helper and a workflow to keep keystone and nautobot in sync. The workflow uses the
argoworkflowservice account to add, update, and delete tenant's from Nautobot based on the same operations happening in keystone.